added GetSensorUsageHourly
as this allows you to pull hourly billing based on Cloud calculated billing.
#1375
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added
GetSensorUsageHourly
to_sensor_usage.py
endpoint; tested it in production, and works by providing either hourly or weekly billing usage depending on how billing is calculated. This is part of CrowdStrike documentation and also shows in the billing dashboard how these values are pulled. This helps calculate the Cloud (reserved hourly) usage. The endpoint that is not documented, but works along with getting weekly billing information is:"/billing-dashboards-usage/aggregates/hourly-average/v1"
PULL REQUEST TITLE
Pull Request general description should go here.
Unit test coverage
Bandit analysis
Added features and functionality
Added support for pulling
hourly
billing data frombilling-dashboard-usage
endpoint on top of the weekly-average values.Issues resolved
Other